-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change absolute paths to relative paths in docs #4698
Conversation
/skip-all |
docs/aks-installation.md
Outdated
@@ -73,7 +73,7 @@ you can deploy Antrea as follows: | |||
``` | |||
|
|||
To deploy the latest version of Antrea (built from the main branch), use the | |||
checked-in [deployment yaml](/build/yamls/antrea-aks.yml): | |||
checked-in [deployment yaml](https://github.com/antrea-io/antrea/blob/main/build/yamls/antrea-aks.yml): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe @tnqn mentioned that the root cause is we should use relative path in the issue comment.
you should update it as following one.
checked-in [deployment yaml](https://github.com/antrea-io/antrea/blob/main/build/yamls/antrea-aks.yml): | |
checked-in [deployment yaml](./build/yamls/antrea-aks.yml): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This wouldn't work because it expands to wrong path and searches for the file in antrea website repo.
Actually any relative path wouldn't work here because these files (mostly yaml) are not present in antrea website github repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If relative path has to work , the folder "build/yamls/" needs to be created on https://antrea.io and then each file needs to be available there, otherwise will have to use absolute GitHub path
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I doubt this is the right way to fix the issue. If you change it to a link, then when you have any changes on a local file, it will jump to a website link which point to a main branch file. I don't think this is what we expected.
Let's see what's @antoninbas and @tnqn 's comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the docs should use relative paths. The link should be ../build/yamls/antrea-aks.yml
here
The right way to fix it is in the scripts which generate the website source (they should do link substitution when applicable: ../build/yamls/antrea-aks.yml -> https://github.com/antrea-io/antrea/blob/<CORRECT TAG>/build/yamls/antrea-aks.yml
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, changed to use relative path.
e238b07
to
464d7f6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while this change is correct, and needed IMO, it doesn't by itself fix issue #4353, and so adding Fixes #4353
to the commit message is incorrect.
in addition to this change, the https://github.com/antrea-io/website/blob/main/scripts/pkg/update-docs.go logic also needs to be improved to translate links to the build/
directory into absolute http links, as I described in a previous comment.
Hi @antoninbas, thanks for your suggestions. I have few questions.
|
|
Signed-off-by: Kumar Atish <atish.iaf@gmail.com>
464d7f6
to
bd07c67
Compare
/skip-all |
Signed-off-by: Kumar Atish <atish.iaf@gmail.com>
No description provided.